Add metadata discovery endpoints for curves and exports#1774
Open
louispt1 wants to merge 4 commits into
Open
Conversation
This was referenced Jun 29, 2026
Member
|
Smart thinking with the registry, as the exports are not available as models. A few questions:
Although I like the direction you are taking, this might need some more thought and design? A first step could be a hardcoded |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
PyETM previously hard-coded the list of available curves and exports. Any new output required changes in pyetm too. These endpoints let pyetm discover available outputs at runtime so a new curve or export can be added to ETEngine without cascading changes.
Implemented changes
GET /api/v3/curves/metadatareturning all registered hourly output curves with their name, type, and descriptionGET /api/v3/exports/metadatareturning all registered annual exports with their name and descriptionCurveMetadataRegistry, a registry populated at startup via an initialiser; curves and exports register themselves in their respective controllersRelated
Goes with this pyetm PR and this documentation PR
Checklist